The latest updates on your projects. Learn more about Vercel for Git ↗︎

Oh sick @pierremtb! I was just about to ask how it handles a long change log before you updated the image, perfect.

Could we get the markdown to render as HTML?

My only thoughts while mocking up this were:

1. Show a Zoo logomark in the overlay so that it feels more like an official notice
2. Reuse the styling we have on the "Alpha" pill from the onboarding to highlight the version number
3. Render the markdown to HTML to get better list styling especially

(Ignore the button styling and the fact that this modal has opened over the /file page view. The buttons are the next look-and-feel and I haven't gotten a good mockup of the home view yet)

Awesome thank you @franknoirot! I'll update it to match the mockup.

Yeah we can use Marked.parse from https://github.com/ts-stack/markdown that we already depend on and inject the result. Just have to figure out how to do it safely

With v0.16.0. We're still missing the bullet points (due to inheritance and I really know how to fix it yet). Will update to main

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.45%. Comparing base (dd51eec) to head (9809c85).
Report is 4 commits behind head on main.

@@           Coverage Diff           @@
##             main    #1738   +/-   ##
=======================================
  Coverage   86.45%   86.45%           
=======================================
  Files          54       54           
  Lines       22424    22424           
=======================================
  Hits        19387    19387           
  Misses       3037     3037           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Moved to draft until we merge #1400 (already rebased on it)

Yeah no worries on the bullet points, I might be able to take a look at the CSS and fix in a follow-up PR if you should me how to test it in dev @pierremtb.

@franknoirot Sounds good! Let's wait for the next update, this branch is easier to test when it's a version behind :)

@franknoirot Waiting on another nightly build to verify that the regular update flow still works as expected. After that I think we should trigger a release, and then get on with this one

Okkkkk @franknoirot we need this merged sooner than later actually 😅 I don't know how I missed this during the migration to tauri v2 #1400

The built-in dialog with an automatic update check was removed, use the Rust and JS APIs to check for and install updates instead.
from https://beta.tauri.app/guides/upgrade-migrate/from-tauri-1/#migrate-to-updater-plugin

We can fake a nightly build locally and point to https://storage.googleapis.com/dl.kittycad.io/releases/modeling-app/nightly/last_update.json with the following

VERSION=24.4.16 yarn bump-jsons
echo "$(jq --arg url 'https://dl.zoo.dev/releases/modeling-app/nightly/last_update.json' \
            '.plugins.updater.endpoints[]=$url' src-tauri/tauri.release.conf.json --indent 2)" > src-tauri/tauri.release.conf.json
echo "$(jq --arg id 'dev.zoo.modeling-app-nightly' \
            '.identifier=$id' src-tauri/tauri.release.conf.json --indent 2)" > src-tauri/tauri.release.conf.json
echo "$(jq --arg name 'Zoo Modeling App (Nightly)' \
            '.productName=$name' src-tauri/tauri.release.conf.json --indent 2)" > src-tauri/tauri.release.conf.json
yarn tauri build -b -c ./src-tauri/tauri.release.conf.json
./src-tauri/target/release/Zoo\ Modeling\ App\ \(Nightly\)